Freephoneline, voip.ms, and googletalk dialplan request

[azrobert]

Also, is there any way to determine T.38 protocol is, in fact, being used during a fax call from the call status screen in an Obi202?

Can't help with this.
You should start a new topic with this question.

[Webslinger]

Try changing rule <00:$1> in the AA DigitMap to: 00

Now 00 will be sent to the AA outbound route.

Then add the following rule to the beginning of the AA outbound route:
{00:sp1($1)},

I'm not getting a callback using this method, or at least, my phone isn't ringing (I do see that AA is making an outbound call, but phone isn't ringing). Anyway, I'm probably doing something stupid. I'll read over your notes again. Sorry for troubling you

[Webslinger]

Can't help with this.
You should start a new topic with this question.

Okay, thank you

[Webslinger]

Physical Interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|*67|*67[2-9]xxxxxxxxx|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|#1XX.S3|**0|***|222222222)
OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Msp3):sp3},{(Msp2):sp2}

Service Provider -> ITSP Profile A -> DigitMap:
([2-9]xxxxxxxxx|<311:4163922489>|*67|*67[2-9]xxxxxxxxx|*98|911)

Service Provider -> ITSP Profile B -> DigitMap:
DigitMap: (<#1:>XX.)

Service Provider -> ITSP Profile C -> DigitMap:
DigitMap: (1xxxxxxxxxx)

I didn't know if you just dial *67 or *67 plus a 10 digit number, so I allowed for both.

Dialing #1 plus a number will be routed out SP2.
When you code XX. in a digit map there will be a 10 second delay.
I changed it to a 3 second delay.
If you get more specific with the format of the numbers dialed, you can improve on this.

222222222 is the OBi echo test.

Hi,

I've noticed the capacity to use both speedial, as setup via the obitalk portal, and obi to obi calling does not work in this dialplan.

My attempts to add this back have failed (outbound call routing not working). Any assistance would be appreciated.

Thank you

[azrobert]

I'm not sure what you are asking.
Are you saying only OBi to OBi calls are not working or did everything stop working?

The easiest way to call another OBi is to setup a Speed Dial like this:
pp(200123456)                 200123456 is the OBi number of the target OBi

Or do you want to dial the 9 digit OBi number of the target OBi?

Do you want to route outbound calls to a trunk on another OBi?

Please post the OBiTalk Service InboundCallRoute from the target OBi.
I can check if the OBiTalk setup process did something to prevent the OBi from ringing.

Voice Services -> OBiTalk Service -> InboundCallRoute

[Webslinger]

Sorry, I'm out shopping at the moment, and I'll provide what you ask when I'm home later.

But **9 gives me a busy signal.

3# does as well

[azrobert]

I removed all the **n code, so **9 won't work.
Speed dials should still work.

If Speed Dial 3 is **9200123456 change it to pp(200123456)

[azrobert]

You probably have code in the OBiTalk inbound route to send these calls to the Auto Attendant. If you want the call to go directly to the phone port without the AA do this:
Voice Services -> OBiTalk Service -> InboundCallRoute: ph

If you want to make outbound calls on the 2nd OBi, I can show you how without the AA.

[Webslinger]

Please post the OBiTalk Service InboundCallRoute from the target OBi.

Code Select Expand

{(290xxxxxx)>(xx.):SP1},{(290xxxxxx):aa},{ph,ph2}


Speed dial 1 is set to softphone, and I can't change it. That has **9 in it.

Speed dial 3 is set to username@boston.voip.ms (sip uri call)



1# gives me a busy signal

3# gives me a busy signal

[Webslinger]

I was trying to fiddle around with the digit map and outbound call route on phone port 1. I guess based on your response that was the wrong approach.

I was getting outbound error messages anyway, so what I was trying to do didn't work, regardless.

[azrobert]

Are you trying to call another OBi ATA or the OBI softphone?

Just setup another Speed Dial with PP(290123456)
There should be a blank entry at the end of the speed dial list.

If you want to use the Phone Port DigitMap and OutboundCallRoute:

Add  |xxxxxxxxx to the end of the PP DigitMap
Add ,{(Mpp):pp} to the end of the PP OutboundCallRoute.

Now dial the 9 digit OBi number.

[Webslinger]

Are you trying to call another OBi ATA

Not at the moment

The one I was trying to call was just taken offline due to a holiday trip

or the OBI softphone?

I was trying to ring both.

I also tried doing a SIP URI call, and that didn't work either.
I tried username@boston.voip.ms and pp('username@boston.voip.ms')
I only got a fast busy signal

I guess that has something to do with [^*#]@@. not being present in my digitmaps.

Just setup another Speed Dial with PP(290123456)

I can't test now that the other OBI ATA I wanted to dial has been taken offline.
I was hoping the speed dial feature would work, regardless of what I'm trying to call.

There should be a blank entry at the end of the speed dial list.

Yes, I'm able to keep adding lines.

If you want to use the Phone Port DigitMap and OutboundCallRoute:

Add  |xxxxxxxxx to the end of the PP DigitMap
Add ,{(Mpp):pp} to the end of the PP OutboundCallRoute.

Now dial the 9 digit OBi number.

Okay, thank you

[azrobert]

I also tried doing a SIP URI call, and that didn't work either.
I tried username@boston.voip.ms and pp('username@boston.voip.ms')
I only got a fast busy signal

I guess that has something to do with [^*#]@@. not being present in my digitmaps.

Speed dials with an SIP URI are NOT validated by the DigitMap.
They are routed directly to the SP number specified.
The correct syntax is:
sp2(username@boston.voip.ms)

The SP number must point to an SP trunk defined as SIP, so the above example SP2 must be defined as SIP.

[azrobert]

I also tried doing a SIP URI call, and that didn't work either.
I tried username@boston.voip.ms and pp('username@boston.voip.ms')
I only got a fast busy signal

I guess that has something to do with [^*#]@@. not being present in my digitmaps.

I thought about this and you are correct.
If you code a speed dial like this "username@boston.voip.ms" it will be routed to the DigitMap and [^*#]@@. will validate it. You would also need a rule like this {([^*#]@@.):sp2} in the OutboundCallroute. It would also have to be the last rule because [^*#]@@. will match almost anything.

Anyway, my last post is a better method.

[Webslinger]

Great. Thank you very much for your help!

[Webslinger]

The SP number must point to an SP trunk defined as SIP

Sorry, I don't believe I understand this. Where and how would it be defined as "SIP".

so the above example SP2 must be defined as SIP

I apologize for my stupidity, but are you just saying SP2 must be the same SIP service provider as the SIP URI I'm trying to connect to?

[Webslinger]

Just setup another Speed Dial with PP(290123456)

Is it possible to test calling my own Obi202 using this method (ringing phone port 2, or something)?
Hmm. Doesn't seem to work.

[azrobert]

SIP protocol found here:
Service Providers -> ITSP Profile X General -> SignalingProtocol
The choices are Google Voice or SIP.

SP2 has to be defined as SIP with any provider.
You are re-using SP2 to connect to a 2nd provider.
There are 8 Voice Gateways definitions you can also point to SP2, so theoretically there can be an unlimited number of trunks using SP2.
The trunk defined on SP2 can register to the provider and can be used for inbound and outbound calls.
All the other trunks using SP2 cannot be registered, so they can only be used for outbound calls.

You can't call yourself via the OBiTalk network.
You will get a response of "Unknown".

[Webslinger]

The choices are Google Voice or SIP.

SP2 has to be defined as SIP with any provider.

Okay, thank you

You are re-using SP2 to connect to a 2nd provider.
There are 8 Voice Gateways definitions you can also point to SP2, so theoretically there can be an unlimited number of trunks using SP2.
The trunk defined on SP2 can register to the provider and can be used for inbound and outbound calls.
All the other trunks using SP2 cannot be registered, so they can only be used for outbound calls.

Okay, I understand this. Thanks

You can't call yourself via the OBiTalk network.
You will get a response of "Unknown".

And that would be the reason for a busy signal? It doesn't even seem as though the attempt to connect is being made with pp(myobinumber) in speed dial (in the fourth line), and pressing 4#, for example.

[azrobert]

I'm getting the same quick busy when calling myself, but I can successfully call another OBi ATA.

If my memory is correct in the past you would get a response code 404, which means Not Found and an IVR message saying the call failed. I tried this a long time ago before I had multiple OBi ATAs. Maybe 2 years.